Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48a3cf6d5425fa73010f413c16dda69588f9fef4cfc47da4c065af9b26aaff6d

Tx prefix hash: 994a6d80ba5150c7a84938474b9350c9450cbd0b557d8b975f70e949a197c27a
Tx public key: 5977eb1e635d9821388d57aa11cab74ea4a157aa3f6676c6ddf6b7f01239777c
Timestamp: 1736918160 Timestamp [UCT]: 2025-01-15 05:16:00 Age [y:d:h:m:s]: 00:153:13:53:21
Block: 1197662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109485 RingCT/type: yes/0
Extra: 015977eb1e635d9821388d57aa11cab74ea4a157aa3f6676c6ddf6b7f01239777c02110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 579f2dfa319c96477f9d96bc15e4d226018a645dc19f8ec83f21bb51de2982b8 0.600000000000 1684275 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": 1197672, "vin": [ { "gen": { "height": 1197662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "579f2dfa319c96477f9d96bc15e4d226018a645dc19f8ec83f21bb51de2982b8" } } ], "extra": [ 1, 89, 119, 235, 30, 99, 93, 152, 33, 56, 141, 87, 170, 17, 202, 183, 78, 164, 161, 87, 170, 63, 102, 118, 198, 221, 246, 183, 240, 18, 57, 119, 124, 2, 17, 0, 0, 0, 15, 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