Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8f84d687858bb515ad526316742af136d94a89881f222e6c1dc87917aa21673

Tx prefix hash: f7ca854a0ee2cb5f74e71a517634596d6aaa5a7eb9a32c6e39c92c2716d82f0c
Tx public key: 4be6c4b453ce4ee9ad002604bb8b95991fea70e4adb0a71e5c38a7e20e8a4d3c
Timestamp: 1582973128 Timestamp [UCT]: 2020-02-29 10:45:28 Age [y:d:h:m:s]: 04:338:15:19:29
Block: 73948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135521 RingCT/type: yes/0
Extra: 014be6c4b453ce4ee9ad002604bb8b95991fea70e4adb0a71e5c38a7e20e8a4d3c0211000001f0724f989b000000000000000000

1 output(s) for total of 349.124540842000 dcy

stealth address amount amount idx
00: a3fbfb2c20c992fe260d532ab59bdce16602b0325a47ce0cd147e915973ca28b 349.124540842000 136665 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": 73958, "vin": [ { "gen": { "height": 73948 } } ], "vout": [ { "amount": 349124540842, "target": { "key": "a3fbfb2c20c992fe260d532ab59bdce16602b0325a47ce0cd147e915973ca28b" } } ], "extra": [ 1, 75, 230, 196, 180, 83, 206, 78, 233, 173, 0, 38, 4, 187, 139, 149, 153, 31, 234, 112, 228, 173, 176, 167, 30, 92, 56, 167, 226, 14, 138, 77, 60, 2, 17, 0, 0, 1, 240, 114, 79, 152, 155, 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