Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de8d72be5046d6dbb5593004d33b8cfd7f29e56347d20ab372ea50094d6dc468

Tx prefix hash: 807acb1e1d53334d3f79bd9fbf44e652e5535cb6a7f93c99ea52ebce332132e1
Tx public key: 8d366709e8ff463976e325257e64b6e2ed343f0d79109e3da39692d98bc142b7
Timestamp: 1706371695 Timestamp [UCT]: 2024-01-27 16:08:15 Age [y:d:h:m:s]: 01:069:09:40:53
Block: 944545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310688 RingCT/type: yes/0
Extra: 018d366709e8ff463976e325257e64b6e2ed343f0d79109e3da39692d98bc142b702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0534f3109725ae3a69f16bce56b3ad06a083c094ea7f0abf82d6d21f8fa4f2f3 0.600000000000 1402821 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": 944555, "vin": [ { "gen": { "height": 944545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0534f3109725ae3a69f16bce56b3ad06a083c094ea7f0abf82d6d21f8fa4f2f3" } } ], "extra": [ 1, 141, 54, 103, 9, 232, 255, 70, 57, 118, 227, 37, 37, 126, 100, 182, 226, 237, 52, 63, 13, 121, 16, 158, 61, 163, 150, 146, 217, 139, 193, 66, 183, 2, 17, 0, 0, 0, 2, 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