Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63d545135de29f4195f56a407d5b0f330ef8a8ef12869289a5eec15ac9aa5305

Tx prefix hash: 40055a7c7d73a5355afdcb71cf16e0b4ebf8964985dd36d24df5add67e01d55a
Tx public key: 0e788f3a8b3520e01cfd4263f5b65886747ce04fcef61ff486d91403c2a1518f
Timestamp: 1669379919 Timestamp [UCT]: 2022-11-25 12:38:39 Age [y:d:h:m:s]: 02:047:16:23:08
Block: 638790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556014 RingCT/type: yes/0
Extra: 010e788f3a8b3520e01cfd4263f5b65886747ce04fcef61ff486d91403c2a1518f02110000000283600029000000000000000000

1 output(s) for total of 4.692708294000 dcy

stealth address amount amount idx
00: 7afac7d137cc3b3162d3e64f4e795c98d40a98f8549b4fa8372e53ca3a5c2453 4.692708294000 1078419 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": 638800, "vin": [ { "gen": { "height": 638790 } } ], "vout": [ { "amount": 4692708294, "target": { "key": "7afac7d137cc3b3162d3e64f4e795c98d40a98f8549b4fa8372e53ca3a5c2453" } } ], "extra": [ 1, 14, 120, 143, 58, 139, 53, 32, 224, 28, 253, 66, 99, 245, 182, 88, 134, 116, 124, 224, 79, 206, 246, 31, 244, 134, 217, 20, 3, 194, 161, 81, 143, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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