Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07feaded507e3c8efc5ce451ce0c319a8b506926ca71a0210bea51cf8b4221b2

Tx prefix hash: 8c3527858b2bdc634d43c0b55bc39d7c5a0b77cff278336b0eeafa65f02a2b29
Tx public key: a780d59b72fd8e15f21c34f191cbb02ebebe6fd4a23af9b20c4245c6dc3774c2
Timestamp: 1711661539 Timestamp [UCT]: 2024-03-28 21:32:19 Age [y:d:h:m:s]: 01:079:00:11:15
Block: 988442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317364 RingCT/type: yes/0
Extra: 01a780d59b72fd8e15f21c34f191cbb02ebebe6fd4a23af9b20c4245c6dc3774c202110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d4b2cdeb5d1f971f3b0c4048d25fe2f84d55ef4c04c2dbf8641462bc1276157 0.600000000000 1448721 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": 988452, "vin": [ { "gen": { "height": 988442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d4b2cdeb5d1f971f3b0c4048d25fe2f84d55ef4c04c2dbf8641462bc1276157" } } ], "extra": [ 1, 167, 128, 213, 155, 114, 253, 142, 21, 242, 28, 52, 241, 145, 203, 176, 46, 190, 190, 111, 212, 162, 58, 249, 178, 12, 66, 69, 198, 220, 55, 116, 194, 2, 17, 0, 0, 0, 7, 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