Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105cfd15e45de61d7bccd8bca501e6e6cbb04b71c1e808dc2931b8377c08eaf1

Tx prefix hash: 3715092f8a9117b2c5cbb7752c579f286ff232a9f7e75ee545494a249908b492
Tx public key: 449673ba9bb0a2c1937848b0d5b0ddff073100fc4b4e7986cd3c156118c7d8f5
Timestamp: 1709884652 Timestamp [UCT]: 2024-03-08 07:57:32 Age [y:d:h:m:s]: 00:321:07:16:54
Block: 973706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229943 RingCT/type: yes/0
Extra: 01449673ba9bb0a2c1937848b0d5b0ddff073100fc4b4e7986cd3c156118c7d8f502110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9981ec2403bb91eef579f956cc493f7c0db1c44aa6ecb30064e5ae8bec9481bd 0.600000000000 1433641 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": 973716, "vin": [ { "gen": { "height": 973706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9981ec2403bb91eef579f956cc493f7c0db1c44aa6ecb30064e5ae8bec9481bd" } } ], "extra": [ 1, 68, 150, 115, 186, 155, 176, 162, 193, 147, 120, 72, 176, 213, 176, 221, 255, 7, 49, 0, 252, 75, 78, 121, 134, 205, 60, 21, 97, 24, 199, 216, 245, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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