Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95450851b938e04876c76fc10a1bb0fc3c952f4ad6488fe7a6b40a64b7146130

Tx prefix hash: 34b474dea4eda19ecabfd0ee6fcf2626cd59768482fcfff07ce7c8961092e348
Tx public key: 70b8fd18f266bb3141d04e25572677e14c2f04208fd9c3d27df3cf0e112f0262
Timestamp: 1732520189 Timestamp [UCT]: 2024-11-25 07:36:29 Age [y:d:h:m:s]: 00:128:16:05:17
Block: 1161253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91759 RingCT/type: yes/0
Extra: 0170b8fd18f266bb3141d04e25572677e14c2f04208fd9c3d27df3cf0e112f02620211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 722ada0adc5eac34eb61b3b1665f2df2478dfe2f5e2f941edc9399fdec9ad25b 0.600000000000 1646904 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": 1161263, "vin": [ { "gen": { "height": 1161253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "722ada0adc5eac34eb61b3b1665f2df2478dfe2f5e2f941edc9399fdec9ad25b" } } ], "extra": [ 1, 112, 184, 253, 24, 242, 102, 187, 49, 65, 208, 78, 37, 87, 38, 119, 225, 76, 47, 4, 32, 143, 217, 195, 210, 125, 243, 207, 14, 17, 47, 2, 98, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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