Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d44491f4bb176893e4422536cf0a0bfeb20f7668dd254de0ce04396d7c3d15

Tx prefix hash: 0d3c9c9956200fe23d325b0bcd4d0e51aa675c82def4012033d8d8d6ba4fed54
Tx public key: 1b8cbd38f9443515bc8123b76d9d1aac192f3e87986364d5190168eccd78aa5a
Timestamp: 1716739668 Timestamp [UCT]: 2024-05-26 16:07:48 Age [y:d:h:m:s]: 00:325:19:25:26
Block: 1030533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232860 RingCT/type: yes/0
Extra: 011b8cbd38f9443515bc8123b76d9d1aac192f3e87986364d5190168eccd78aa5a0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0ec1412d5117cc5bb948e941fbf373d9d7c379ddeacd4594eb31dc1ab8e1115 0.600000000000 1498788 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": 1030543, "vin": [ { "gen": { "height": 1030533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0ec1412d5117cc5bb948e941fbf373d9d7c379ddeacd4594eb31dc1ab8e1115" } } ], "extra": [ 1, 27, 140, 189, 56, 249, 68, 53, 21, 188, 129, 35, 183, 109, 157, 26, 172, 25, 47, 62, 135, 152, 99, 100, 213, 25, 1, 104, 236, 205, 120, 170, 90, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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