Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d4cddda6a8cf174b846e4bb400edb14e467d90996c2cee4e2ce4b257dd48b3a

Tx prefix hash: cdf6260f11124656b4eb1a861bdb77f16cc2f6bb52bb9543bc885dba1436bec4
Tx public key: 46c1818ddb0a3a667f1dae0a0c7ba4bf2d5612f549fe59ae1f139e803bf4f094
Timestamp: 1716737715 Timestamp [UCT]: 2024-05-26 15:35:15 Age [y:d:h:m:s]: 00:295:15:35:06
Block: 1030521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211292 RingCT/type: yes/0
Extra: 0146c1818ddb0a3a667f1dae0a0c7ba4bf2d5612f549fe59ae1f139e803bf4f0940211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14f363bfe0bd1f26902f4aa910ef3f9986c121346fc63a58774c6470be6a5129 0.600000000000 1498776 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": 1030531, "vin": [ { "gen": { "height": 1030521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14f363bfe0bd1f26902f4aa910ef3f9986c121346fc63a58774c6470be6a5129" } } ], "extra": [ 1, 70, 193, 129, 141, 219, 10, 58, 102, 127, 29, 174, 10, 12, 123, 164, 191, 45, 86, 18, 245, 73, 254, 89, 174, 31, 19, 158, 128, 59, 244, 240, 148, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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