Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0381e77361e0ef6dc522f926188e0d281a64b514c56819fe0c837f3daf099a82

Tx prefix hash: 385a8bfa3c4d99e2e5df21f6c4dee8e09e9346cb316980a6a1c6f59d8e8534c0
Tx public key: a54f626cb68333dd9a2c94cd458c70ab855cb02fec24ef3ca6073e15958debbb
Timestamp: 1681076488 Timestamp [UCT]: 2023-04-09 21:41:28 Age [y:d:h:m:s]: 02:005:18:51:39
Block: 735101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526296 RingCT/type: yes/0
Extra: 01a54f626cb68333dd9a2c94cd458c70ab855cb02fec24ef3ca6073e15958debbb02110000000275e3f0e9000000000000000000

1 output(s) for total of 2.250637014000 dcy

stealth address amount amount idx
00: 4a83cfa7a35aa2fb6f7d6bf45653b7f421c3c9837a4b5589fee9438426198f37 2.250637014000 1181390 of 0

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": 735111, "vin": [ { "gen": { "height": 735101 } } ], "vout": [ { "amount": 2250637014, "target": { "key": "4a83cfa7a35aa2fb6f7d6bf45653b7f421c3c9837a4b5589fee9438426198f37" } } ], "extra": [ 1, 165, 79, 98, 108, 182, 131, 51, 221, 154, 44, 148, 205, 69, 140, 112, 171, 133, 92, 176, 47, 236, 36, 239, 60, 166, 7, 62, 21, 149, 141, 235, 187, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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