Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4cc272884298ac0d1de90539d831c0d352a3413d6674967b4e61c0e3d9725090

Tx prefix hash: cae8517bce2bbdb346cf68328b7f1193c3eebe181f864246d453e5129c44751a
Tx public key: 407269ca733f1f6b7a59e7e100a83a0700571ddd2d3ab96bef5130c0a465f261
Timestamp: 1633287027 Timestamp [UCT]: 2021-10-03 18:50:27 Age [y:d:h:m:s]: 03:152:09:22:47
Block: 345979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 885722 RingCT/type: yes/0
Extra: 01407269ca733f1f6b7a59e7e100a83a0700571ddd2d3ab96bef5130c0a465f2610211000000105d7cc334000000000000000000

1 output(s) for total of 43.815561251000 dcy

stealth address amount amount idx
00: f02f308012a3e0134c256962ce10cecaee036c2a858afb7db21a3144d9135ba1 43.815561251000 709603 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 345989, "vin": [ { "gen": { "height": 345979 } } ], "vout": [ { "amount": 43815561251, "target": { "key": "f02f308012a3e0134c256962ce10cecaee036c2a858afb7db21a3144d9135ba1" } } ], "extra": [ 1, 64, 114, 105, 202, 115, 63, 31, 107, 122, 89, 231, 225, 0, 168, 58, 7, 0, 87, 29, 221, 45, 58, 185, 107, 239, 81, 48, 192, 164, 101, 242, 97, 2, 17, 0, 0, 0, 16, 93, 124, 195, 52, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8