Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b9a91f12ee0c6b29e0a15a592c18a2388c99a69dcaa95637b2d2c9f3863dd29

Tx prefix hash: 68cc5df97dcee43e2ae5b2dd4e214e6c7c0e8e26df421d85fefaad2bcac8eb61
Tx public key: 4ae1d7cb31fe6c326886035f7ece9bfae9622c7316184076fde9b1f33699e42f
Timestamp: 1713385028 Timestamp [UCT]: 2024-04-17 20:17:08 Age [y:d:h:m:s]: 00:360:23:53:19
Block: 1002710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258085 RingCT/type: yes/0
Extra: 014ae1d7cb31fe6c326886035f7ece9bfae9622c7316184076fde9b1f33699e42f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a00eee788b70d57ee7ae77bf83fe6214862b7560fbc49a3cf437a63dd3f26a38 0.600000000000 1463230 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": 1002720, "vin": [ { "gen": { "height": 1002710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a00eee788b70d57ee7ae77bf83fe6214862b7560fbc49a3cf437a63dd3f26a38" } } ], "extra": [ 1, 74, 225, 215, 203, 49, 254, 108, 50, 104, 134, 3, 95, 126, 206, 155, 250, 233, 98, 44, 115, 22, 24, 64, 118, 253, 233, 177, 243, 54, 153, 228, 47, 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