Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4e8178274e012435fceb9796bc2e0bc02f1fd1376f955daad37b5362c78ca7

Tx prefix hash: bb15a90c64bb69f7fb700c6772334bc186dc4a0edf3d5d898b4bc37f00399da5
Tx public key: af6a9a144de99dffc40160e73a85862a3d37e3d6aa4b1c15f896c1fc6f357b5e
Timestamp: 1728370952 Timestamp [UCT]: 2024-10-08 07:02:32 Age [y:d:h:m:s]: 01:031:06:37:50
Block: 1126964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280718 RingCT/type: yes/0
Extra: 01af6a9a144de99dffc40160e73a85862a3d37e3d6aa4b1c15f896c1fc6f357b5e021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad8d3972b28ec5f1fa1bbfd906f1a3f605b8bb3d6b10d49a020eb18153db1dba 0.600000000000 1609763 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": 1126974, "vin": [ { "gen": { "height": 1126964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad8d3972b28ec5f1fa1bbfd906f1a3f605b8bb3d6b10d49a020eb18153db1dba" } } ], "extra": [ 1, 175, 106, 154, 20, 77, 233, 157, 255, 196, 1, 96, 231, 58, 133, 134, 42, 61, 55, 227, 214, 170, 75, 28, 21, 248, 150, 193, 252, 111, 53, 123, 94, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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