Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0fb6d2159482d6e96c945d6f5749506bfaebf5ef872a6f6335dcff94d97073a

Tx prefix hash: 72aa44855ca25e048691bb857fba71d76f302ffee9e49a20e5c26ba588fc82d6
Tx public key: 5945eb0cf9a5a9e91d6583ef58a813bfe51f1c1947269dd58b89a56e0ecf9a14
Timestamp: 1731203375 Timestamp [UCT]: 2024-11-10 01:49:35 Age [y:d:h:m:s]: 00:138:21:44:17
Block: 1150358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99090 RingCT/type: yes/0
Extra: 015945eb0cf9a5a9e91d6583ef58a813bfe51f1c1947269dd58b89a56e0ecf9a14021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4723627a23b70d765ea103db328058ff8611ebaa814e863ae216d2b436a16ff9 0.600000000000 1635647 of 15

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": 1150368, "vin": [ { "gen": { "height": 1150358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4723627a23b70d765ea103db328058ff8611ebaa814e863ae216d2b436a16ff9" } } ], "extra": [ 1, 89, 69, 235, 12, 249, 165, 169, 233, 29, 101, 131, 239, 88, 168, 19, 191, 229, 31, 28, 25, 71, 38, 157, 213, 139, 137, 165, 110, 14, 207, 154, 20, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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