Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 411af30d6d9b9ff795ca8c532aae150da8729fa4f884bad086ea4b7b9fe6432a

Tx prefix hash: 47087b9768202e874ff79f3e41aa121e31d2d8b50ca30a18eef5e01068f097a8
Tx public key: 834c796f47de75fb8985f34328d44480b80af4d4ee1dd12d38ab049b11809ba4
Timestamp: 1717695119 Timestamp [UCT]: 2024-06-06 17:31:59 Age [y:d:h:m:s]: 01:009:00:57:53
Block: 1038451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267258 RingCT/type: yes/0
Extra: 01834c796f47de75fb8985f34328d44480b80af4d4ee1dd12d38ab049b11809ba402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b0b9d05d218d6c5e6b4bb636f1937c4713975135202c4b60ba8f5950e556cf2 0.600000000000 1507012 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": 1038461, "vin": [ { "gen": { "height": 1038451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b0b9d05d218d6c5e6b4bb636f1937c4713975135202c4b60ba8f5950e556cf2" } } ], "extra": [ 1, 131, 76, 121, 111, 71, 222, 117, 251, 137, 133, 243, 67, 40, 212, 68, 128, 184, 10, 244, 212, 238, 29, 209, 45, 56, 171, 4, 155, 17, 128, 155, 164, 2, 17, 0, 0, 0, 5, 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