Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cedb3586c0e21a98319198514db24f0511adf7c9ef962f3ee954453bdad3c069

Tx prefix hash: 9a77fbcf60c527816d686bf8649f33e45a7691e7cfa96a91f1dc18e4972a59c5
Tx public key: fd7d2d625c2a170041f3a9c2ace54d328ec4b2e70f6cdaa0ce246f9665d23016
Timestamp: 1702609687 Timestamp [UCT]: 2023-12-15 03:08:07 Age [y:d:h:m:s]: 01:331:21:35:43
Block: 913379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496068 RingCT/type: yes/0
Extra: 01fd7d2d625c2a170041f3a9c2ace54d328ec4b2e70f6cdaa0ce246f9665d2301602110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b1ff3a123efcba072796e8daf3f1f3abd85b6486e8ca4480218ffb13c9dc2f1 0.600000000000 1370647 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": 913389, "vin": [ { "gen": { "height": 913379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b1ff3a123efcba072796e8daf3f1f3abd85b6486e8ca4480218ffb13c9dc2f1" } } ], "extra": [ 1, 253, 125, 45, 98, 92, 42, 23, 0, 65, 243, 169, 194, 172, 229, 77, 50, 142, 196, 178, 231, 15, 108, 218, 160, 206, 36, 111, 150, 101, 210, 48, 22, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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