Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 015afc4df9cdd2ff0f6f4e1fcbbf70a8d17e6cf401b240447a124cd53aec0544

Tx prefix hash: 6b1033feacb953284f00e2912ddbc9878253eb04e47169159af36ffd3227eb68
Tx public key: 2700c5e9293ddd45244959c6ccc7395e9064fc670b5b7c917649a5020641301e
Timestamp: 1695545291 Timestamp [UCT]: 2023-09-24 08:48:11 Age [y:d:h:m:s]: 01:206:17:22:49
Block: 855010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408813 RingCT/type: yes/0
Extra: 012700c5e9293ddd45244959c6ccc7395e9064fc670b5b7c917649a5020641301e021100000015e6d27f9c000000000000000000

1 output(s) for total of 0.901564884000 dcy

stealth address amount amount idx
00: 7016b9a8ba90d831e0bf9aae8c5cd4ba02845812e080f532c591e3ee2e8a1be1 0.901564884000 1309008 of 0

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": 855020, "vin": [ { "gen": { "height": 855010 } } ], "vout": [ { "amount": 901564884, "target": { "key": "7016b9a8ba90d831e0bf9aae8c5cd4ba02845812e080f532c591e3ee2e8a1be1" } } ], "extra": [ 1, 39, 0, 197, 233, 41, 61, 221, 69, 36, 73, 89, 198, 204, 199, 57, 94, 144, 100, 252, 103, 11, 91, 124, 145, 118, 73, 165, 2, 6, 65, 48, 30, 2, 17, 0, 0, 0, 21, 230, 210, 127, 156, 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