Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b462f66ee4901f697958a0ce0bcf29a8da334d9d5c37a099e409db3980e85b7f

Tx prefix hash: af27b7a45811f032ce5aa1fac6a460961361812ff7c98f70f9f31cb8dd9ecce9
Tx public key: 2798c473fea30c40a69f1733cafb801a39827c22eac395b7664dcbfb0208c46d
Timestamp: 1702916318 Timestamp [UCT]: 2023-12-18 16:18:38 Age [y:d:h:m:s]: 01:351:15:37:40
Block: 915926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510205 RingCT/type: yes/0
Extra: 012798c473fea30c40a69f1733cafb801a39827c22eac395b7664dcbfb0208c46d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3d3c2fceb3641db499b82f517890029f63e6022fa413c5f55c9386869c7a90a 0.600000000000 1373360 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": 915936, "vin": [ { "gen": { "height": 915926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3d3c2fceb3641db499b82f517890029f63e6022fa413c5f55c9386869c7a90a" } } ], "extra": [ 1, 39, 152, 196, 115, 254, 163, 12, 64, 166, 159, 23, 51, 202, 251, 128, 26, 57, 130, 124, 34, 234, 195, 149, 183, 102, 77, 203, 251, 2, 8, 196, 109, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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