Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c1fa57d302715b5927763aadde8cf3fd36cc577e90c91f3746d29b69caf599

Tx prefix hash: a7cc5c3cdfac398c02fe7008cb52bda45c76b16489123d82b826ddf701a03959
Tx public key: 357b0258049af3b0c1b0c63e3dfe3976e2bb41f815ab6043a068a3c1d0a609cf
Timestamp: 1727615617 Timestamp [UCT]: 2024-09-29 13:13:37 Age [y:d:h:m:s]: 00:223:16:59:33
Block: 1120696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159705 RingCT/type: yes/0
Extra: 01357b0258049af3b0c1b0c63e3dfe3976e2bb41f815ab6043a068a3c1d0a609cf021100000003e914dd15000000000000000000

1 output(s) for total of 0.608010000000 dcy

stealth address amount amount idx
00: ccde53664ac3407c94450c57344f910b726de8de68942c7ce4db43cb40eee02c 0.608010000000 1602701 of 0

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": 1120706, "vin": [ { "gen": { "height": 1120696 } } ], "vout": [ { "amount": 608010000, "target": { "key": "ccde53664ac3407c94450c57344f910b726de8de68942c7ce4db43cb40eee02c" } } ], "extra": [ 1, 53, 123, 2, 88, 4, 154, 243, 176, 193, 176, 198, 62, 61, 254, 57, 118, 226, 187, 65, 248, 21, 171, 96, 67, 160, 104, 163, 193, 208, 166, 9, 207, 2, 17, 0, 0, 0, 3, 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