Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b91379c619f9addffde1a15c28faee368a382a1add46b69c2b9cb06c4a1a38d9

Tx prefix hash: 6b6a4280cec553ad1dc52057e9c27fe06ecaf37776b2e41f83be6c771f34327d
Tx public key: 3a998005e50a6d6e3b433a98f79d09332db941b542965bed7e1abd29cf2c36d0
Timestamp: 1751410913 Timestamp [UCT]: 2025-07-01 23:01:53 Age [y:d:h:m:s]: 00:211:10:54:42
Block: 1316831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149282 RingCT/type: yes/0
Extra: 013a998005e50a6d6e3b433a98f79d09332db941b542965bed7e1abd29cf2c36d002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 553037f0e04e58ffd47ba34e66aabf3670ce36a3e6fefa7e4cdf10db45438ae8 0.600000000000 1804494 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": 1316841, "vin": [ { "gen": { "height": 1316831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "553037f0e04e58ffd47ba34e66aabf3670ce36a3e6fefa7e4cdf10db45438ae8" } } ], "extra": [ 1, 58, 153, 128, 5, 229, 10, 109, 110, 59, 67, 58, 152, 247, 157, 9, 51, 45, 185, 65, 181, 66, 150, 91, 237, 126, 26, 189, 41, 207, 44, 54, 208, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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