Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8f34f73877d5357f150197303c909d251105437b9821d67573e1804dabd4a8

Tx prefix hash: 462d3a0f70c4a384fb905830e05b0e17bd38b7521c3616d97695d9985ca4a7dc
Tx public key: 90f23addd721fbd98a2d191b7424bebbfb546bc1d7cab7de8d0076e9cd4a28b4
Timestamp: 1714268921 Timestamp [UCT]: 2024-04-28 01:48:41 Age [y:d:h:m:s]: 00:321:21:32:35
Block: 1010036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230138 RingCT/type: yes/0
Extra: 0190f23addd721fbd98a2d191b7424bebbfb546bc1d7cab7de8d0076e9cd4a28b402110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 451dab899850d734b0d4d45743d428453ad31692a837509c521a0e7c15c32d15 0.600000000000 1471874 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": 1010046, "vin": [ { "gen": { "height": 1010036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "451dab899850d734b0d4d45743d428453ad31692a837509c521a0e7c15c32d15" } } ], "extra": [ 1, 144, 242, 58, 221, 215, 33, 251, 217, 138, 45, 25, 27, 116, 36, 190, 187, 251, 84, 107, 193, 215, 202, 183, 222, 141, 0, 118, 233, 205, 74, 40, 180, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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