Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe9f37185df1c5e986a94aba851892e36f6e420bcd1d296a2d7130a8147d8d1

Tx prefix hash: fbd9d4ea7a666cdf5ac76d1660426bfbc0fc8d033afe24ca4679eae0396c5899
Tx public key: 6cec7ca2174f85c5406d6c94d32d33db54213420fc6e10e8dce38b7e77066fd7
Timestamp: 1737055769 Timestamp [UCT]: 2025-01-16 19:29:29 Age [y:d:h:m:s]: 00:151:16:46:40
Block: 1198805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108145 RingCT/type: yes/0
Extra: 016cec7ca2174f85c5406d6c94d32d33db54213420fc6e10e8dce38b7e77066fd7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18fce32fde229df98f4c36c45c2f4237e3dc8d149b8845a5501658b14b2c87cf 0.600000000000 1685432 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": 1198815, "vin": [ { "gen": { "height": 1198805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18fce32fde229df98f4c36c45c2f4237e3dc8d149b8845a5501658b14b2c87cf" } } ], "extra": [ 1, 108, 236, 124, 162, 23, 79, 133, 197, 64, 109, 108, 148, 211, 45, 51, 219, 84, 33, 52, 32, 252, 110, 16, 232, 220, 227, 139, 126, 119, 6, 111, 215, 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