Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22578f2e88d4562e8e11161e249118af3bdfd52fd40293bf95ee3bff68f0d672

Tx prefix hash: a612a3913629ce0b73730871a4f972e811a71a6e82db7593b9489b22779f00f4
Tx public key: 879f248ddf98079ae9ad57022f8e92eb4d053db8f7c358e756b3834a704cd762
Timestamp: 1725636455 Timestamp [UCT]: 2024-09-06 15:27:35 Age [y:d:h:m:s]: 00:289:23:47:01
Block: 1104288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206911 RingCT/type: yes/0
Extra: 01879f248ddf98079ae9ad57022f8e92eb4d053db8f7c358e756b3834a704cd762021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29c7d41f7d38fd0cd025d4d7147dcf4d03c13e2fb7ad957530514c82fcf44dac 0.600000000000 1581371 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": 1104298, "vin": [ { "gen": { "height": 1104288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29c7d41f7d38fd0cd025d4d7147dcf4d03c13e2fb7ad957530514c82fcf44dac" } } ], "extra": [ 1, 135, 159, 36, 141, 223, 152, 7, 154, 233, 173, 87, 2, 47, 142, 146, 235, 77, 5, 61, 184, 247, 195, 88, 231, 86, 179, 131, 74, 112, 76, 215, 98, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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