Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d40e018de30bc0982aa52dc967c225c1fa019ab3640e82373b77db39db27ef4d

Tx prefix hash: a71cf2ed78fbd01883a8f31fda2a4600bc6a2610f513f98b255fb040a3cb8c06
Tx public key: 497b8a1badb36524e522a156637047c52a1c0c07cb6748ff40f927453a36d0f3
Timestamp: 1714028686 Timestamp [UCT]: 2024-04-25 07:04:46 Age [y:d:h:m:s]: 01:193:07:51:20
Block: 1008044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396811 RingCT/type: yes/0
Extra: 01497b8a1badb36524e522a156637047c52a1c0c07cb6748ff40f927453a36d0f302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc58efb602d10d89170cc0bbb7bb0cf252289df99e1fc0447b9cf838b534e3ce 0.600000000000 1469510 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": 1008054, "vin": [ { "gen": { "height": 1008044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc58efb602d10d89170cc0bbb7bb0cf252289df99e1fc0447b9cf838b534e3ce" } } ], "extra": [ 1, 73, 123, 138, 27, 173, 179, 101, 36, 229, 34, 161, 86, 99, 112, 71, 197, 42, 28, 12, 7, 203, 103, 72, 255, 64, 249, 39, 69, 58, 54, 208, 243, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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