Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bc6e201477491ab4f529ef615f293b6afe49e3322fc2673e620f61df788a88a

Tx prefix hash: e69b9075c0fd7aca36727aed8374190c69132fc09ede383d79dc8e366b40a726
Tx public key: 7d084004107be88f1d892a5c0e9a266f6d994b7d4faac48852b16eb0bbeb7fe0
Timestamp: 1740923963 Timestamp [UCT]: 2025-03-02 13:59:23 Age [y:d:h:m:s]: 00:256:20:46:59
Block: 1230561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181332 RingCT/type: yes/0
Extra: 017d084004107be88f1d892a5c0e9a266f6d994b7d4faac48852b16eb0bbeb7fe0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4cba520cfb72dc221133e9c93fb06aa813e677e2fc2cf69d500568bebff6afa 0.600000000000 1717460 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": 1230571, "vin": [ { "gen": { "height": 1230561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4cba520cfb72dc221133e9c93fb06aa813e677e2fc2cf69d500568bebff6afa" } } ], "extra": [ 1, 125, 8, 64, 4, 16, 123, 232, 143, 29, 137, 42, 92, 14, 154, 38, 111, 109, 153, 75, 125, 79, 170, 196, 136, 82, 177, 110, 176, 187, 235, 127, 224, 2, 17, 0, 0, 0, 4, 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