Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b46dac33368ffd487b608b2ae173860aa7f249e438f7581681912242e395d93a

Tx prefix hash: ea32d9697baa494ef0a9b4de86ed42a2a86cf9d6a04e489e0226f20ba6cf4c0b
Tx public key: 0ee0780f3ca44e22b30d3390fe06052ccdf13297641d67d8bf97b7a3723f05aa
Timestamp: 1701790645 Timestamp [UCT]: 2023-12-05 15:37:25 Age [y:d:h:m:s]: 01:130:14:53:36
Block: 906589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354529 RingCT/type: yes/0
Extra: 010ee0780f3ca44e22b30d3390fe06052ccdf13297641d67d8bf97b7a3723f05aa02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.608267026000 dcy

stealth address amount amount idx
00: 6fdaf2ffdd4f288ef3da26ab4071ef47517dd55ecba7e048a2fb23383c6cdd9d 0.608267026000 1363526 of 0

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": 906599, "vin": [ { "gen": { "height": 906589 } } ], "vout": [ { "amount": 608267026, "target": { "key": "6fdaf2ffdd4f288ef3da26ab4071ef47517dd55ecba7e048a2fb23383c6cdd9d" } } ], "extra": [ 1, 14, 224, 120, 15, 60, 164, 78, 34, 179, 13, 51, 144, 254, 6, 5, 44, 205, 241, 50, 151, 100, 29, 103, 216, 191, 151, 183, 163, 114, 63, 5, 170, 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