Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cd80d5208882f6751e5035c7fde9b09c516eb22137f90c64c1d0928afadede9

Tx prefix hash: 69e0258a02ca898527ac5bfeaac3d85c6f6f20cdd7bd863e3568814eab7354c3
Tx public key: dc2540c575677fbf0209e0aa89e9cbb68f9a825a7984283c85d90b6e424016ed
Timestamp: 1730115504 Timestamp [UCT]: 2024-10-28 11:38:24 Age [y:d:h:m:s]: 00:161:15:31:06
Block: 1141347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115344 RingCT/type: yes/0
Extra: 01dc2540c575677fbf0209e0aa89e9cbb68f9a825a7984283c85d90b6e424016ed021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b05b27bd51a1d4ada77c7bb6c4a546a347bbff77544ca3a0a0abba8a66d28f9 0.600000000000 1625154 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": 1141357, "vin": [ { "gen": { "height": 1141347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b05b27bd51a1d4ada77c7bb6c4a546a347bbff77544ca3a0a0abba8a66d28f9" } } ], "extra": [ 1, 220, 37, 64, 197, 117, 103, 127, 191, 2, 9, 224, 170, 137, 233, 203, 182, 143, 154, 130, 90, 121, 132, 40, 60, 133, 217, 11, 110, 66, 64, 22, 237, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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