Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04b2d79c66f23bff628e372c442ecdac9ecb50fda758f850471744433534666f

Tx prefix hash: e64f6fe39ee088901fb2e1fcd5cdc480739a9a61ddea4d08999432cf56ab39b9
Tx public key: 85629cfdc903a7f6d1f26391bc05049b042a4c81555b3bd4ce322f7d16717b82
Timestamp: 1713293545 Timestamp [UCT]: 2024-04-16 18:52:25 Age [y:d:h:m:s]: 01:067:07:40:21
Block: 1001939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308904 RingCT/type: yes/0
Extra: 0185629cfdc903a7f6d1f26391bc05049b042a4c81555b3bd4ce322f7d16717b8202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92b8085a7f5c991d6a0320a6c9f9431a2d54abc388feebcacbcc67a53235e007 0.600000000000 1462453 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": 1001949, "vin": [ { "gen": { "height": 1001939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92b8085a7f5c991d6a0320a6c9f9431a2d54abc388feebcacbcc67a53235e007" } } ], "extra": [ 1, 133, 98, 156, 253, 201, 3, 167, 246, 209, 242, 99, 145, 188, 5, 4, 155, 4, 42, 76, 129, 85, 91, 59, 212, 206, 50, 47, 125, 22, 113, 123, 130, 2, 17, 0, 0, 0, 2, 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