Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d8e7c3783de76850effdfaf93a4f809c92b4dbdc20e330cb95365732c5ddf7

Tx prefix hash: e2770cd00e224426007b981b70cd1c2f5f663bd7fc57f60c46171f532caa8c1d
Tx public key: 97f670e3a72187425d9179e4a14ecce0d81a2e984316c5aa1d02c415c2211fd3
Timestamp: 1726613383 Timestamp [UCT]: 2024-09-17 22:49:43 Age [y:d:h:m:s]: 00:067:23:41:46
Block: 1112377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48607 RingCT/type: yes/0
Extra: 0197f670e3a72187425d9179e4a14ecce0d81a2e984316c5aa1d02c415c2211fd302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcff9e48a354b3c95fb2a12ae5838bce1ccd5d2b10ba90858fc681e83b97514a 0.600000000000 1591676 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": 1112387, "vin": [ { "gen": { "height": 1112377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcff9e48a354b3c95fb2a12ae5838bce1ccd5d2b10ba90858fc681e83b97514a" } } ], "extra": [ 1, 151, 246, 112, 227, 167, 33, 135, 66, 93, 145, 121, 228, 161, 78, 204, 224, 216, 26, 46, 152, 67, 22, 197, 170, 29, 2, 196, 21, 194, 33, 31, 211, 2, 17, 0, 0, 0, 7, 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