Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe58a7cc18bab22580088f86e3e508118eb685e7bb7e10448d5fdd5c99d9e57a

Tx prefix hash: 488b378328e768f10a0a4d2c89fd290926fdd6a82b87272e6c40a5c48f9df860
Tx public key: d744a7ce1cdb2e2ca781f02f6915bddb17ec21dc0716010875a807c8e2199fe1
Timestamp: 1752987080 Timestamp [UCT]: 2025-07-20 04:51:20 Age [y:d:h:m:s]: 00:069:13:55:02
Block: 1329311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48444 RingCT/type: yes/0
Extra: 01d744a7ce1cdb2e2ca781f02f6915bddb17ec21dc0716010875a807c8e2199fe1021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7b54f1296eaf230a4cabdd1c585aa9c2272458586e4b561698f1b4cc0467297 0.600000000000 1817088 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": 1329321, "vin": [ { "gen": { "height": 1329311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7b54f1296eaf230a4cabdd1c585aa9c2272458586e4b561698f1b4cc0467297" } } ], "extra": [ 1, 215, 68, 167, 206, 28, 219, 46, 44, 167, 129, 240, 47, 105, 21, 189, 219, 23, 236, 33, 220, 7, 22, 1, 8, 117, 168, 7, 200, 226, 25, 159, 225, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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