Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e72a095b01c6a71619086af7f2c5f605358a7e769152c9e5a85052589f313a50

Tx prefix hash: bdf778fbb1b86bedf2ec9441436a96f72c88b1ce8f6e34319875dd68079ec415
Tx public key: 91d7e637fb732a4239bd7d330ffa3a2bac23072d519163061fe2910cb7ac393f
Timestamp: 1761202301 Timestamp [UCT]: 2025-10-23 06:51:41 Age [y:d:h:m:s]: 00:102:02:21:42
Block: 1396034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72912 RingCT/type: yes/0
Extra: 0191d7e637fb732a4239bd7d330ffa3a2bac23072d519163061fe2910cb7ac393f021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a58b2d6949a088fd6a74b308cc8f85c39b26cf2dc1d2c280cdba70d87e6ab9b 0.600000000000 1884319 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": 1396044, "vin": [ { "gen": { "height": 1396034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a58b2d6949a088fd6a74b308cc8f85c39b26cf2dc1d2c280cdba70d87e6ab9b" } } ], "extra": [ 1, 145, 215, 230, 55, 251, 115, 42, 66, 57, 189, 125, 51, 15, 250, 58, 43, 172, 35, 7, 45, 81, 145, 99, 6, 31, 226, 145, 12, 183, 172, 57, 63, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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