Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656ad8627145c0b8d3605d15f60961d70dd6b8d606d280c1f6984ffd74db826b

Tx prefix hash: 0483b1ef058751b0b032da039523ebb7715c917e6dfb820e70270ed05f8f5535
Tx public key: 34b272c77dae2aeca805a6cc5c979a29572603bdc65ba6c1083c8871e824827a
Timestamp: 1684167787 Timestamp [UCT]: 2023-05-15 16:23:07 Age [y:d:h:m:s]: 02:007:08:09:24
Block: 760739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527378 RingCT/type: yes/0
Extra: 0134b272c77dae2aeca805a6cc5c979a29572603bdc65ba6c1083c8871e824827a021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.850785476000 dcy

stealth address amount amount idx
00: c7dea654fee6a8ad3d0d78ebcc67d7f01aba3626f59dfe72669cd9d18dd2f3b4 1.850785476000 1209372 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": 760749, "vin": [ { "gen": { "height": 760739 } } ], "vout": [ { "amount": 1850785476, "target": { "key": "c7dea654fee6a8ad3d0d78ebcc67d7f01aba3626f59dfe72669cd9d18dd2f3b4" } } ], "extra": [ 1, 52, 178, 114, 199, 125, 174, 42, 236, 168, 5, 166, 204, 92, 151, 154, 41, 87, 38, 3, 189, 198, 91, 166, 193, 8, 60, 136, 113, 232, 36, 130, 122, 2, 17, 0, 0, 0, 3, 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