Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f516bf1f31d90268d1aba1559d14383705dc3e1873c3692fc8fc3a141285818d

Tx prefix hash: a325f7950c8796bd57b10c69d75287811ed01585bd9ebb33cafcc9f4d7ee74b7
Tx public key: 9595520d217592c419cbeb9760ae625cdc6d0faba6b6e7a049f22970956e74b5
Timestamp: 1735676124 Timestamp [UCT]: 2024-12-31 20:15:24 Age [y:d:h:m:s]: 00:134:07:39:35
Block: 1187381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95816 RingCT/type: yes/0
Extra: 019595520d217592c419cbeb9760ae625cdc6d0faba6b6e7a049f22970956e74b50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8bb2f50fca6742cf12a2b057702e7dab7175bba8103383e43a3f7af02dc4f59 0.600000000000 1673870 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": 1187391, "vin": [ { "gen": { "height": 1187381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8bb2f50fca6742cf12a2b057702e7dab7175bba8103383e43a3f7af02dc4f59" } } ], "extra": [ 1, 149, 149, 82, 13, 33, 117, 146, 196, 25, 203, 235, 151, 96, 174, 98, 92, 220, 109, 15, 171, 166, 182, 231, 160, 73, 242, 41, 112, 149, 110, 116, 181, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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