Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14dcad10025ed1a86cfe91e540f56d4f94547f2893d852598953c5429f3c2214

Tx prefix hash: dbbf411c6321979451b2ee37bd3098b3546f1fc3f98259f3af1a6aaa6f18beed
Tx public key: 47d83d5a8abb9b8dc1c15fd2923fd7d44f72295e65d8a619304e76d374066e16
Timestamp: 1725549886 Timestamp [UCT]: 2024-09-05 15:24:46 Age [y:d:h:m:s]: 00:192:19:52:13
Block: 1103566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137675 RingCT/type: yes/0
Extra: 0147d83d5a8abb9b8dc1c15fd2923fd7d44f72295e65d8a619304e76d374066e16021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd90db06caf3fbedcca834845c7bae54881e41c4e4318a7c5bfc73db985c0d46 0.600000000000 1580447 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": 1103576, "vin": [ { "gen": { "height": 1103566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd90db06caf3fbedcca834845c7bae54881e41c4e4318a7c5bfc73db985c0d46" } } ], "extra": [ 1, 71, 216, 61, 90, 138, 187, 155, 141, 193, 193, 95, 210, 146, 63, 215, 212, 79, 114, 41, 94, 101, 216, 166, 25, 48, 78, 118, 211, 116, 6, 110, 22, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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