Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e358d7bddb6f9d990c590f05803cc4fbc6dbea537c23d159bedc7bccd671f2f

Tx prefix hash: 994425d671c8ee9015bc01676ef7686da72f8a0b10e14d6e6ca30e601295f552
Tx public key: f45c0a620de6e0bd78a00c2a14d0a0849dbd9e16e9539163e421163019f2d856
Timestamp: 1723872954 Timestamp [UCT]: 2024-08-17 05:35:54 Age [y:d:h:m:s]: 00:304:05:26:37
Block: 1089670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217241 RingCT/type: yes/0
Extra: 01f45c0a620de6e0bd78a00c2a14d0a0849dbd9e16e9539163e421163019f2d85602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 369e2f370c79ad90b1bb7fe0027ee2e8a2891982fa80930ee115ef1e8f4aa41b 0.600000000000 1564293 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": 1089680, "vin": [ { "gen": { "height": 1089670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "369e2f370c79ad90b1bb7fe0027ee2e8a2891982fa80930ee115ef1e8f4aa41b" } } ], "extra": [ 1, 244, 92, 10, 98, 13, 230, 224, 189, 120, 160, 12, 42, 20, 208, 160, 132, 157, 189, 158, 22, 233, 83, 145, 99, 228, 33, 22, 48, 25, 242, 216, 86, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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