Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49aa454ec71de9df3f6b478f3d001d2a5f8bf559d55212506c3e83dd4c04afb3

Tx prefix hash: a0dc0ae7f081afc581413188431e5b6ad13c524077b27bcce9df51d16fe23862
Tx public key: 109dc6fedd4fced74aade7f1297f44522edfb1e58b9dd4d114c500a5bfc947f3
Timestamp: 1740471916 Timestamp [UCT]: 2025-02-25 08:25:16 Age [y:d:h:m:s]: 00:262:02:21:06
Block: 1226805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185088 RingCT/type: yes/0
Extra: 01109dc6fedd4fced74aade7f1297f44522edfb1e58b9dd4d114c500a5bfc947f3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 675ea26ad5ee6cbcb25f425bf45772fa90c06207328b419d72aebb95742771f9 0.600000000000 1713678 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": 1226815, "vin": [ { "gen": { "height": 1226805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "675ea26ad5ee6cbcb25f425bf45772fa90c06207328b419d72aebb95742771f9" } } ], "extra": [ 1, 16, 157, 198, 254, 221, 79, 206, 215, 74, 173, 231, 241, 41, 127, 68, 82, 46, 223, 177, 229, 139, 157, 212, 209, 20, 197, 0, 165, 191, 201, 71, 243, 2, 17, 0, 0, 0, 2, 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