Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2980f282f60d593ec68a6f0abd42642815a7bba46a3b9d0ba2df21165f3f359e

Tx prefix hash: ddd596cc2b0cfe36f224101ab5fc66951f4e06fa12be8aa6c3b8626995f6bc5d
Tx public key: e4a91620ed1f82b397bb2ee4021ae9b714318a343905dcdeef63d4ba38ef2562
Timestamp: 1713833219 Timestamp [UCT]: 2024-04-23 00:46:59 Age [y:d:h:m:s]: 01:191:13:47:51
Block: 1006428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395563 RingCT/type: yes/0
Extra: 01e4a91620ed1f82b397bb2ee4021ae9b714318a343905dcdeef63d4ba38ef256202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ed60528402e069cd2269382e42867a97b7b88115fcfd7b6f0eadc3d15bd314a 0.600000000000 1467458 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": 1006438, "vin": [ { "gen": { "height": 1006428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ed60528402e069cd2269382e42867a97b7b88115fcfd7b6f0eadc3d15bd314a" } } ], "extra": [ 1, 228, 169, 22, 32, 237, 31, 130, 179, 151, 187, 46, 228, 2, 26, 233, 183, 20, 49, 138, 52, 57, 5, 220, 222, 239, 99, 212, 186, 56, 239, 37, 98, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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