Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54938db90b5eef572e131577fe97515da0fe690a967011c3961c0140a37fa17f

Tx prefix hash: b1c22cd9c105c9bad56d6cbc6d34854028e4d6f14abae00391a814e311fc1265
Tx public key: 1f1c371aba6d6d1082cdf8cd21d29fa519955b33e86cee3d52bb5b226f355d03
Timestamp: 1742071821 Timestamp [UCT]: 2025-03-15 20:50:21 Age [y:d:h:m:s]: 00:323:00:29:10
Block: 1240083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228510 RingCT/type: yes/0
Extra: 011f1c371aba6d6d1082cdf8cd21d29fa519955b33e86cee3d52bb5b226f355d030211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1747af856d882ce238ed3f5f841e91c6d7b1fa80f4a95dc02222cd9df44b295 0.600000000000 1727048 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": 1240093, "vin": [ { "gen": { "height": 1240083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1747af856d882ce238ed3f5f841e91c6d7b1fa80f4a95dc02222cd9df44b295" } } ], "extra": [ 1, 31, 28, 55, 26, 186, 109, 109, 16, 130, 205, 248, 205, 33, 210, 159, 165, 25, 149, 91, 51, 232, 108, 238, 61, 82, 187, 91, 34, 111, 53, 93, 3, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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