Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a15c27dd67d28352a167163d016c9c6104f645972d4ab826dd282f2760e44105

Tx prefix hash: cb8824f934f1a155089ee46dd5136af4e59369ee66548eb7c9b717c5dacaf265
Tx public key: a676ea7a790a99df3d0f999074bf7245f769e958d3e995c3cfb4d12abe5daf05
Timestamp: 1726662017 Timestamp [UCT]: 2024-09-18 12:20:17 Age [y:d:h:m:s]: 00:236:15:53:43
Block: 1112783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168992 RingCT/type: yes/0
Extra: 01a676ea7a790a99df3d0f999074bf7245f769e958d3e995c3cfb4d12abe5daf0502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 863e8f4fd9568ed54822407f498bf0d564cf92d789a7ed90b0da1a9e7fddb081 0.600000000000 1592226 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": 1112793, "vin": [ { "gen": { "height": 1112783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "863e8f4fd9568ed54822407f498bf0d564cf92d789a7ed90b0da1a9e7fddb081" } } ], "extra": [ 1, 166, 118, 234, 122, 121, 10, 153, 223, 61, 15, 153, 144, 116, 191, 114, 69, 247, 105, 233, 88, 211, 233, 149, 195, 207, 180, 209, 42, 190, 93, 175, 5, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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