Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bbbb1e8674adc792872e2650ca6e4a768dbf63a9f0d01d7639705f4d50c606f

Tx prefix hash: 29f48f03a7be2c0679c80581a178384629f7eaa8d27db2dc8fc259aaefad4178
Tx public key: 6fde9cd40b490742658da108f906bd60643b0db01165b7a11b3be54af2d5c5ee
Timestamp: 1704825813 Timestamp [UCT]: 2024-01-09 18:43:33 Age [y:d:h:m:s]: 01:085:20:49:55
Block: 931735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322485 RingCT/type: yes/0
Extra: 016fde9cd40b490742658da108f906bd60643b0db01165b7a11b3be54af2d5c5ee0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8abc70dc7514c7c6c7ea022ac8a1bd37f3a12af7fbe8c7661b185e0e1bf88bd1 0.600000000000 1389639 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": 931745, "vin": [ { "gen": { "height": 931735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8abc70dc7514c7c6c7ea022ac8a1bd37f3a12af7fbe8c7661b185e0e1bf88bd1" } } ], "extra": [ 1, 111, 222, 156, 212, 11, 73, 7, 66, 101, 141, 161, 8, 249, 6, 189, 96, 100, 59, 13, 176, 17, 101, 183, 161, 27, 59, 229, 74, 242, 213, 197, 238, 2, 17, 0, 0, 0, 4, 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