Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 146a112a3e728b3d1665ce810431447efc7984f43894f98ca3f2350d60dac074

Tx prefix hash: 66519f99146ad6a967d351ef8471e96afd88867ac2d4df83132c1b8af0a3a240
Tx public key: b2195f52c8f218bbb797021699182e6f96a1a812620fa86637ed251d49a0ff9f
Timestamp: 1711787060 Timestamp [UCT]: 2024-03-30 08:24:20 Age [y:d:h:m:s]: 01:004:17:33:23
Block: 989493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264307 RingCT/type: yes/0
Extra: 01b2195f52c8f218bbb797021699182e6f96a1a812620fa86637ed251d49a0ff9f02110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 544c346a6ee4b3896223e69fe0f079a5d44c780d7c9d36dbb7b29aefc581cb1a 0.600000000000 1449792 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": 989503, "vin": [ { "gen": { "height": 989493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "544c346a6ee4b3896223e69fe0f079a5d44c780d7c9d36dbb7b29aefc581cb1a" } } ], "extra": [ 1, 178, 25, 95, 82, 200, 242, 24, 187, 183, 151, 2, 22, 153, 24, 46, 111, 150, 161, 168, 18, 98, 15, 168, 102, 55, 237, 37, 29, 73, 160, 255, 159, 2, 17, 0, 0, 0, 14, 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