Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74b06608498dcf85dfb9352e47680bed4aaf8b50fb405c7bcba785ad58e563e8

Tx prefix hash: d07157ecfa134185809c48b1f8bd8b19f3c0c1e6f4a37bcd6db0b3a0adc4a0df
Tx public key: 6483f753135aee064a0e6e3fbe145bb7e06234395c62384596e9953475f2d717
Timestamp: 1737342003 Timestamp [UCT]: 2025-01-20 03:00:03 Age [y:d:h:m:s]: 00:149:09:31:51
Block: 1201131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106526 RingCT/type: yes/0
Extra: 016483f753135aee064a0e6e3fbe145bb7e06234395c62384596e9953475f2d7170211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b158f4cd8849f476bf1d5ad5841df8e4eeeb331418c2d4a26cd9f20618013a13 0.600000000000 1687780 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": 1201141, "vin": [ { "gen": { "height": 1201131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b158f4cd8849f476bf1d5ad5841df8e4eeeb331418c2d4a26cd9f20618013a13" } } ], "extra": [ 1, 100, 131, 247, 83, 19, 90, 238, 6, 74, 14, 110, 63, 190, 20, 91, 183, 224, 98, 52, 57, 92, 98, 56, 69, 150, 233, 149, 52, 117, 242, 215, 23, 2, 17, 0, 0, 0, 9, 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