Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d6245f94f7512e1db297b1cd02e18951bb84a5cde5d2f673d2ee0d356063d9f

Tx prefix hash: ba1bcbcabd646ced84702ca434eb1f4d406825c129d34ffa6c639bf5249b1f5a
Tx public key: 77587b81071f41fd0a06d8a4041093c5518aa9c80b834d43c4f038e88a65200d
Timestamp: 1719107485 Timestamp [UCT]: 2024-06-23 01:51:25 Age [y:d:h:m:s]: 00:265:23:33:40
Block: 1050139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190084 RingCT/type: yes/0
Extra: 0177587b81071f41fd0a06d8a4041093c5518aa9c80b834d43c4f038e88a65200d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d20a9993ea671c14ea784c0ca283a1c7082b34c0ed02121ce6fb880e29edc49 0.600000000000 1520300 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": 1050149, "vin": [ { "gen": { "height": 1050139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d20a9993ea671c14ea784c0ca283a1c7082b34c0ed02121ce6fb880e29edc49" } } ], "extra": [ 1, 119, 88, 123, 129, 7, 31, 65, 253, 10, 6, 216, 164, 4, 16, 147, 197, 81, 138, 169, 200, 11, 131, 77, 67, 196, 240, 56, 232, 138, 101, 32, 13, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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