Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 617ae00ef22777366c4fd8cb6adb32c41b4edc62b9a32a28389448b2227d89cf

Tx prefix hash: 87026a78f3111e3b3ebfcf70945c2b227d7d1a2303f30072550e4ab199bbb223
Tx public key: d32c62696f62789fdc422faca910d189192429547d2e0bcf1a1df82ebc4042d6
Timestamp: 1701565074 Timestamp [UCT]: 2023-12-03 00:57:54 Age [y:d:h:m:s]: 01:124:21:27:40
Block: 904719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350412 RingCT/type: yes/0
Extra: 01d32c62696f62789fdc422faca910d189192429547d2e0bcf1a1df82ebc4042d60211000000014b8f5122000000000000000000

1 output(s) for total of 0.617007386000 dcy

stealth address amount amount idx
00: 13245ead90638513bc41248f89577d8607bde6e431db7903c9df1bda300f82f6 0.617007386000 1361490 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": 904729, "vin": [ { "gen": { "height": 904719 } } ], "vout": [ { "amount": 617007386, "target": { "key": "13245ead90638513bc41248f89577d8607bde6e431db7903c9df1bda300f82f6" } } ], "extra": [ 1, 211, 44, 98, 105, 111, 98, 120, 159, 220, 66, 47, 172, 169, 16, 209, 137, 25, 36, 41, 84, 125, 46, 11, 207, 26, 29, 248, 46, 188, 64, 66, 214, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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