Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 022e2edb4c1746b535d5248dc8eb42fb2f0207fb7aed3a5f52228ee9d564a1a9

Tx prefix hash: 36c74137215d5d55e941b8c79a2e77873edc51ade9d444cfcd48b88725a8480c
Tx public key: f9589df1d8d65c9b32d97cc7b1ca8da1e56f61e82a196474e29593e589f088bf
Timestamp: 1706737143 Timestamp [UCT]: 2024-01-31 21:39:03 Age [y:d:h:m:s]: 01:070:17:34:16
Block: 947582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311636 RingCT/type: yes/0
Extra: 01f9589df1d8d65c9b32d97cc7b1ca8da1e56f61e82a196474e29593e589f088bf02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d53b2a4c2272182cdaeacd6f1191b6a2ebd629eb967ce0d115534da2b34b7f7a 0.600000000000 1405934 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": 947592, "vin": [ { "gen": { "height": 947582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d53b2a4c2272182cdaeacd6f1191b6a2ebd629eb967ce0d115534da2b34b7f7a" } } ], "extra": [ 1, 249, 88, 157, 241, 216, 214, 92, 155, 50, 217, 124, 199, 177, 202, 141, 161, 229, 111, 97, 232, 42, 25, 100, 116, 226, 149, 147, 229, 137, 240, 136, 191, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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