Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be7c775b45889a65b83b06f073d79dec458b1370dc85f756a4eca8fb8b92ea88

Tx prefix hash: 02ad65fb62d042a38c1803f81fc83303499508495519660ce8f15aeb4bc1bfd4
Tx public key: fcb3760320fa29028aa152b133e3ae000d0338a0a1173cab14b60324fb956d6c
Timestamp: 1710418271 Timestamp [UCT]: 2024-03-14 12:11:11 Age [y:d:h:m:s]: 01:067:17:39:29
Block: 978137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309423 RingCT/type: yes/0
Extra: 01fcb3760320fa29028aa152b133e3ae000d0338a0a1173cab14b60324fb956d6c02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f0637e725591addcb9445abe8c8c8e8e8c14ca4b5f1d80c623e38334a993fcf 0.600000000000 1438154 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": 978147, "vin": [ { "gen": { "height": 978137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f0637e725591addcb9445abe8c8c8e8e8c14ca4b5f1d80c623e38334a993fcf" } } ], "extra": [ 1, 252, 179, 118, 3, 32, 250, 41, 2, 138, 161, 82, 177, 51, 227, 174, 0, 13, 3, 56, 160, 161, 23, 60, 171, 20, 182, 3, 36, 251, 149, 109, 108, 2, 17, 0, 0, 0, 8, 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