Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3415d2166474629a2e37a4c37694352d9db48fb701cb42a85a7583ae30f70a

Tx prefix hash: fbc15c1439e696a2fec1b906e9e322e84bdff5ff362474d2303fc2e9011fcd61
Tx public key: 31b7d7c72e49111a4a9ed4daacf165a26b290181b3e68e19edb34eb6a0ecfae4
Timestamp: 1694021849 Timestamp [UCT]: 2023-09-06 17:37:29 Age [y:d:h:m:s]: 01:175:16:40:12
Block: 842365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386639 RingCT/type: yes/0
Extra: 0131b7d7c72e49111a4a9ed4daacf165a26b290181b3e68e19edb34eb6a0ecfae402110000000375e3f0e9000000000000000000

1 output(s) for total of 0.992876291000 dcy

stealth address amount amount idx
00: f65c856392a5095e6682be541f1c2c1d6cc9765d8cd7b0524813972092afd757 0.992876291000 1295483 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": 842375, "vin": [ { "gen": { "height": 842365 } } ], "vout": [ { "amount": 992876291, "target": { "key": "f65c856392a5095e6682be541f1c2c1d6cc9765d8cd7b0524813972092afd757" } } ], "extra": [ 1, 49, 183, 215, 199, 46, 73, 17, 26, 74, 158, 212, 218, 172, 241, 101, 162, 107, 41, 1, 129, 179, 230, 142, 25, 237, 179, 78, 182, 160, 236, 250, 228, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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