Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a44b07d148d025f44096e1e671ed31129750f499de26823b9db2df13e06ddcd

Tx prefix hash: 4fb43dc64613244dbbef67cac5bdb71a1e7ff9803ee2e41b032609cc47da6e2c
Tx public key: 42a0e3c3feead2d19f1f5375cb22cc43289046c78adfd10b79e72340d0abc1d3
Timestamp: 1673162113 Timestamp [UCT]: 2023-01-08 07:15:13 Age [y:d:h:m:s]: 02:329:17:55:33
Block: 670096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755120 RingCT/type: yes/0
Extra: 0142a0e3c3feead2d19f1f5375cb22cc43289046c78adfd10b79e72340d0abc1d302110000000552542ceb000000000000000000

1 output(s) for total of 3.695674718000 dcy

stealth address amount amount idx
00: 0f66aa5425cbc71a8b7410e2f4c8bedd387ce3b2b0a774034ff18e65d52ae6d3 3.695674718000 1111469 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": 670106, "vin": [ { "gen": { "height": 670096 } } ], "vout": [ { "amount": 3695674718, "target": { "key": "0f66aa5425cbc71a8b7410e2f4c8bedd387ce3b2b0a774034ff18e65d52ae6d3" } } ], "extra": [ 1, 66, 160, 227, 195, 254, 234, 210, 209, 159, 31, 83, 117, 203, 34, 204, 67, 40, 144, 70, 199, 138, 223, 209, 11, 121, 231, 35, 64, 208, 171, 193, 211, 2, 17, 0, 0, 0, 5, 82, 84, 44, 235, 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