Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f210cd2efdfcfa79677f0aef7e8701a0ed79c1166e4534afc7b50dc1a7ebb951

Tx prefix hash: 4a47b7410928ab2deb8801b534f1a05e6a774da9266439a8b75dcd26e578ba2c
Tx public key: e7126869a6d2c6cbcddd4e00bee9bc42c4f627c113f9495506a9ec66d732ede4
Timestamp: 1737823575 Timestamp [UCT]: 2025-01-25 16:46:15 Age [y:d:h:m:s]: 00:147:01:11:30
Block: 1205131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104790 RingCT/type: yes/0
Extra: 01e7126869a6d2c6cbcddd4e00bee9bc42c4f627c113f9495506a9ec66d732ede4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81b68ee8527c3d0245e0e27571cb65abe0a6ed490e43c25b8d56f156a9d81e07 0.600000000000 1691828 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": 1205141, "vin": [ { "gen": { "height": 1205131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81b68ee8527c3d0245e0e27571cb65abe0a6ed490e43c25b8d56f156a9d81e07" } } ], "extra": [ 1, 231, 18, 104, 105, 166, 210, 198, 203, 205, 221, 78, 0, 190, 233, 188, 66, 196, 246, 39, 193, 19, 249, 73, 85, 6, 169, 236, 102, 215, 50, 237, 228, 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