Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 003feaf2a6c085f2bd318c8139c247095505db5b309aad84013a0f7b64c2fbd2

Tx prefix hash: 2a3b71bbe4ae0b3f9283ebd842531e5c50c1fd706a0b52ad28e59a1a93a0ae8f
Tx public key: 53da6183610982e4146083f453ccc5f7b6ba3420183c38cc808d1b922a3ceeaa
Timestamp: 1706789179 Timestamp [UCT]: 2024-02-01 12:06:19 Age [y:d:h:m:s]: 01:304:17:21:50
Block: 948015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476608 RingCT/type: yes/0
Extra: 0153da6183610982e4146083f453ccc5f7b6ba3420183c38cc808d1b922a3ceeaa02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ae2bc66120d0166169d666bc3159ab3e8c39f508973c5349a53974ebc51fba6 0.600000000000 1406385 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": 948025, "vin": [ { "gen": { "height": 948015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ae2bc66120d0166169d666bc3159ab3e8c39f508973c5349a53974ebc51fba6" } } ], "extra": [ 1, 83, 218, 97, 131, 97, 9, 130, 228, 20, 96, 131, 244, 83, 204, 197, 247, 182, 186, 52, 32, 24, 60, 56, 204, 128, 141, 27, 146, 42, 60, 238, 170, 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