Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18942c8c96aace484b5d2111b9ed57afd6a3ba85fb311531c26b829b6b70c055

Tx prefix hash: 41d4f5bbc489ac37b47155b6e665d982e4be8049f9e967654fc01fac26bdc670
Tx public key: 75d7453e3fc868d36c417dcc0d927e9eea77a8bd49e5cb41a8a4daef4d26e770
Timestamp: 1734933671 Timestamp [UCT]: 2024-12-23 06:01:11 Age [y:d:h:m:s]: 00:176:16:29:14
Block: 1181271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125966 RingCT/type: yes/0
Extra: 0175d7453e3fc868d36c417dcc0d927e9eea77a8bd49e5cb41a8a4daef4d26e770021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cb69967af18d6e1a280f498afa180c361b6dd5616de0be8570af4f311468f29 0.600000000000 1667688 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": 1181281, "vin": [ { "gen": { "height": 1181271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cb69967af18d6e1a280f498afa180c361b6dd5616de0be8570af4f311468f29" } } ], "extra": [ 1, 117, 215, 69, 62, 63, 200, 104, 211, 108, 65, 125, 204, 13, 146, 126, 158, 234, 119, 168, 189, 73, 229, 203, 65, 168, 164, 218, 239, 77, 38, 231, 112, 2, 17, 0, 0, 0, 3, 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