Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a0b65209db2856dcd1f75084c15a3eaaabd33aeeb2b7a1cad979707f759664

Tx prefix hash: e26ffed35c17e04cd76244eb390a7b85cd3047b4256d1c34b0fec165e7fdffb4
Tx public key: 9b5b7cefe3654b1d971a83e538951f602172b96fbd0b349d03bc7c6bc991e36b
Timestamp: 1745644677 Timestamp [UCT]: 2025-04-26 05:17:57 Age [y:d:h:m:s]: 00:015:11:59:32
Block: 1269645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11087 RingCT/type: yes/0
Extra: 019b5b7cefe3654b1d971a83e538951f602172b96fbd0b349d03bc7c6bc991e36b0211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8294e761d7d9f2df375ddfd7b4d774483bccf98c29a085f6654f9c9e75d55af 0.600000000000 1756884 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": 1269655, "vin": [ { "gen": { "height": 1269645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8294e761d7d9f2df375ddfd7b4d774483bccf98c29a085f6654f9c9e75d55af" } } ], "extra": [ 1, 155, 91, 124, 239, 227, 101, 75, 29, 151, 26, 131, 229, 56, 149, 31, 96, 33, 114, 185, 111, 189, 11, 52, 157, 3, 188, 124, 107, 201, 145, 227, 107, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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